<p>
  There is no reason to have a <code>main</code> method in a web application.
  It may have been useful for debugging during application development,
  but such a method should never make it into production.
  Having a <code>main</code> method in a web application opens a door to the application logic
  that an attacker may never be able to reach (but watch out if one does!),
  but it is a sloppy practice and indicates that other problems may be present.
</p>
<p>
  This rule raises an issue when a <code>main</code> method is found in a servlet or an EJB.
</p>

<h2>Noncompliant Code Example</h2>
<pre>
public class MyServlet extends HttpServlet {
  public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException {
    if (userIsAuthorized(req)) {
      updatePrices(req);
    }
  }

  public static void main(String[] args) { // Noncompliant
    updatePrices(req);
  }
}
</pre>

<h2>See</h2>
<ul>
  <li><a href="http://cwe.mitre.org/data/definitions/489.html">MITRE, CWE-489</a> - Leftover Debug Code</li>
</ul>
